Update of cell quality derivation parameters

ABSTRACT

According to some embodiments, a method performed by a wireless device for updating measurement configuration comprises receiving a measurement configuration from a network node. The measurement configuration comprises a measurement object that includes at least one cell quality derivation parameter. The wireless device has previously stored measurement results associated with the measurement object. The method further comprises: determining the measurement object includes a reconfigured cell quality derivation parameter that changes the way the wireless device determines the quality of a cell; determining a portion of the previously stored measurement results were computed based on the reconfigured cell quality derivation parameter; and removing the portion of the previously stored measurement results. The method may further comprise resetting timers and removing measurement information associated with the removed measurement results.

TECHNICAL FIELD

Embodiments of the present disclosure are directed to wirelesscommunications and, more particularly, to user equipment (UE) actionswhen receiving updated to cell quality derivation parameters in fifthgeneration (5G) new radio (NR).

BACKGROUND

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Third generation Partnership Project (3GPP) long term evolution (LTE)includes measurement objects that describe how a user equipment (UE)measures a reference signal and how the UE reports the measurements tothe network. The network configures each measurement via a measurementidentifier (measId) that links a measurement object (i.e., a carrierfrequency and a report configuration (reportConfig) that may contain anevent like A1, A2, A6, etc. as defined in 3GPP TS 36.331). LTEspecifications also define a procedure to modify and/or add ameasurement object. Upon receiving a measurement configuration update,the UE deletes measurements associated with the updated measurementobject and resets reporting timers (i.e., the UE discards allmeasurement identifiers associated with the carrier frequency). Theprocedure makes sense for LTE because the measurement object updateslikely relate to the manner in which a UE triggers events (e.g., when anew cell is added/removed from one of the maintained lists (white listsor blacklists), or when new cells are added/removed from the cellspecific offset lists, etc. The procedural text from the radio resourcecontrol (RRC) specifications and the ASN.1 for the E-UTRA measObjecthighlighted below are an example.

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                altTTT-CellsToAddModList, cellsToRemoveList,                blackCellsToRemoveList, whiteCellsToRemoveList,                altTTT-CellsToRemoveList,                measSubframePatternConfigNeigh, measDS-Config,                wlan-ToAddModList and wlan-ToRemoveList;            -   if the received measObject includes the                cellsToRemoveList:                -   for each cellIndex included in the                    cellsToRemoveList:                -    remove the entry with the matching cellIndex from                    the cellsToAddModList;            -   if the received measObject includes the                cellsToAddModList:                -   for each cellIndex value included in the                    cellsToAddModList:                -    if an entry with the matching cellIndex exists in                    the cellsToAddModList:                -    replace the entry with the value received for this                    cellIndex;                -    else:                -    add a new entry for the received cellIndex to            -   if the received measObject includes the                blackCellsToRemoveList:                -   for each cellIndex included in the                    blackCellsToRemoveList:                -    remove the entry with the matching cellIndex from                    the blackCellsToAddModList;

NOTE 1: For each cellIndex included in the blackCellsToRemoveList thatconcerns overlapping ranges of cells, a cell is removed from the blacklist of cells only if all cell indexes containing it are removed.

-   -   if the received measObject includes the blackCellsToAddModList:        -   for each cellIndex included in the blackCellsToAddModList:            -   if an entry with the matching cellIndex is included in                the blackCellsToAddModList:                -   replace the entry with the value received for this                    cellIndex;            -   else:                -   add a new entry for the received cellIndex to the                    blackCellsToAddModList;    -   if the received measObject includes the whiteCellsToRemoveList:        -   for each cellIndex included in the whiteCellsToRemoveList:            -   remove the entry with the matching cellIndex from the                white CellsToAddModList;

NOTE 2: For each cellIndex included in the whiteCellsToRemoveList thatconcerns overlapping ranges of cells, a cell is removed from the whitelist of cells only if all cell indexes containing it are removed.

-   -   if the received measObject includes the whiteCellsToAddModList:        -   for each cellIndex included in the whiteCellsToAddModList:            -   if an entry with the matching cellIndex is included in                the whiteCellsToAddModList:                -   replace the entry with the value received for this                    cellIndex;            -   else:                -   add a new entry for the received cellIndex to the                    whiteCellsToAddModList;    -   if the received measObject includes the        altTTT-CellsToRemoveList:        -   for each cellIndex included in the altTTT-CellsToRemoveList:            -    remove the entry with the matching cellIndex from the                altTTT-CellsToAddModList;

NOTE 3: For each cellIndex included in the altTTT-CellsToRemoveList thatconcerns overlapping ranges of cells, a cell is removed from the list ofcells only if all cell indexes containing it are removed.

-   -   if the received measObject includes the        altTTT-CellsToAddModList:        -   for each cellIndex value included in the            altTTT-CellsToAddModList:            -   if an entry with the matching cellIndex exists in the                altTTT-CellsToAddModList:                -   replace the entry with the value received for this                    cellIndex;            -   else:                -   add a new entry for the received cellIndex to the                    altTTT-CellsToAddModList;    -   if the received measObject includes        measSubframePatternConfigNeigh:        -   set measSubframePatternConfigNeigh within the VarMeasConfig            to the value of the received field    -   if the received measObject includes measDS-Config:        -   if measDS-Config is set to setup:            -   if the received measDS-Config includes the                measCSI-RS-ToRemoveList:                -   for each measCSI-RS-Id included in the                    measCSI-RS-ToRemoveList:                -    remove the entry with the matching measCSI-RS-Id                    from the measCSI-RS-ToAddModList;            -   if the received measDS-Config includes the                measCSI-RS-ToAddModList, for each measCSI-RS-Id value                included in the measCSI-RS-ToAddModList:                -   if an entry with the matching measCSI-RS-Id exists                    in the measCSI-RS-ToAddModList:                -    replace the entry with the value received for this                    measCSI-RS-Id;                -   else:                -    add a new entry for the received measCSI-RS-Id to                    the measCSI-RS-ToAddModList;            -   set other fields of the measDS-Config within the                VarMeasConfig to the value of the received fields;            -   perform the discovery signals measurement timing                configuration procedure as specified in 5.5.2.10;        -   else:            -   release the discovery signals measurement configuration;    -   for each measId associated with this measObjectId in the        measIdList within the VarMeasConfig, if any:        -   remove the measurement reporting entry for this measId from            the VarMeasReportList, if included;        -   stop the periodical reporting timer or timer T321, whichever            one is running, and reset the associated    -   if the received measObject includes the wlan-ToRemoveList:        -   for each WLAN-Identifiers included in the wlan-ToRemoveList:            -   remove the entry with the matching WLAN-Identifiers from                the wlan-ToAddModList;

NOTE 3a: Matching of WLAN-Identifiers requires that all WLAN identifierfields should be same.

-   -   if the received measObject includes the wlan-ToAddModList:        -   for each WLAN-Identifiers included in the wlan-ToAddModList:            -   add a new entry for the received WLAN-Identifiers to the                wlan-ToAddModList;    -   if the received measObject includes the        tx-ResourcePoolToRemoveList:        -   for each v2x-poolIdentity in tx-ResourcePoolToRemoveList:            -   remove the entry with the matching v2x-poolIdentity;                from the tx-ResourcePoolToAddList;        -   if the received measObject includes the            tx-ResourcePoolToAddList:            -   for each v2x-poolIdentity in tx-ResourcePoolToAddList:                -   add a new entry for the received v2x-poolIdentity to                    the tx-ResourcePoolToAddList;

else:

-   -   add a new entry for the received measObject to the        measObjectList within VarMeasConfig; NOTE 4: UE does not need to        retain cellForWhichToReportCGI in the measObject after reporting        cgi-Info.

LTE defines a measurement object using ASN.1. The information element(IE) MeasObjectEUTRA specifies information applicable forintra-frequency or inter-frequency E-UTRA cells.

MeasObjectEUTRA information element -- ASN1START MeasObjectEUTRA ::=SEQUENCE { carrierFreq ARFCN-ValueEUTRA, allowedMeasBandwidthAllowedMeasBandwidth, presenceAntennaPort1 Presence AntennaPort1,neighCellConfig NeighCellConfig, offsetFreq Q-OffsetRange DEFAULT dB0,-- Cell list cellsToRemoveList CellIndexList OPTIONAL, -- Need ONcellsToAddModList CellsToAddModList OPTIONAL, -- Need ON -- Black listblackCellsToRemoveList CellIndexList OPTIONAL, -- Need ONblackCellsToAddModList BlackCellsToAddModList OPTIONAL, -- Need ONcellForWhichToReportCGI PhysCellId OPTIONAL, -- Need ON ...,[[measCycleSCell-r10 MeasCycleSCell-r10 OPTIONAL, -- Need ONmeasSubframePatternConfigNeigh-r10 MeasSubframePatternConfigNeigh-r10OPTIONAL -- Need ON ]], [[widebandRSRQ-Meas-r11 BOOLEAN OPTIONAL -- CondWB-RSRQ ]], [[ altTTT-CellsToRemoveList-r12 CellIndexList OPTIONAL, --Need ON altTTT-CellsToAddModList-r12 AltTTT-CellsToAddModList-r12OPTIONAL, -- Need ON t312-r12 CHOICE { release NULL, setup ENUMERATED{ms0, ms50, ms100, ms200, ms300, ms400, ms500, ms1000} } OPTIONAL, --Need ON reducedMeasPerformance-r12 BOOLEAN OPTIONAL, -- Need ONmeasDS-Config-r12 MeasDS-Config-r12 OPTIONAL -- Need ON ]], [[whiteCellsToRemoveList-r13 CellIndexList OPTIONAL, -- Need ONwhiteCellsToAddModList-r13 WhiteCellsToAddModList-r13 OPTIONAL, -- NeedON rmtc-Config-r13 RMTC-Config-r13 OPTIONAL, -- Need ON carrierFreq-r13ARFCN-ValueEUTRA- v9e0 OPTIONAL -- Need ON ]] } MeasObjectEUTRA-v9e0 ::=SEQUENCE { carrierFreq-v9e0 ARFCN-ValueEUTRA-v9e0 } CellsToAddModList::= SEQUENCE (SIZE (1..maxCellMeas)) OF CellsToAddMod CellsToAddMod ::=SEQUENCE { cellIndex INTEGER (1..maxCellMeas), physCellId PhysCellId,cellIndividualOffset Q-OffsetRange } BlackCellsToAddModList ::= SEQUENCE(SIZE (1..maxCellMeas)) OF BlackCellsToAddMod BlackCellsToAddMod ::=SEQUENCE { cellIndex INTEGER (1..maxCellMeas), physCellIdRangePhysCellIdRange } MeasCycleSCell-r10 ::= ENUMERATED {sf160, sf256,sf320, sf512, sf640, sf1024, sf1280, spare1}MeasSubframePatternConfigNeigh-r10 ::= CHOICE { release NULL, setupSEQUENCE { measSubframePatternNeigh-r10 MeasSubframePattern- r10,measSubframeCellList-r10 MeasSubframeCellList- r10 OPTIONAL -- Condalways } } MeasSubframeCellList-r10 ::= SEQUENCE (SIZE (1..maxCellMeas))OF PhysCellIdRange AltTTT-CellsToAddModList-r12 ::= SEQUENCE (SIZE(1..maxCellMeas)) OF AltTTT- CellsToAddMod-r12 AltTTT-CellsToAddMod-r12::= SEQUENCE { cellIndex-r12 INTEGER (1..maxCellMeas),physCellIdRange-r12 PhysCellIdRange } WhiteCellsToAddModList-r13 ::=SEQUENCE (SIZE (1..maxCellMeas)) OF WhiteCellsToAddMod-r13WhiteCellsToAddMod-r13 ::= SEQUENCE { cellIndex-r13 INTEGER(1..maxCellMeas), physCellIdRange-r13 PhysCellIdRange } RMTC-Config-r13::=CHOICE { release, NULL setup SEQUENCE { rmtc-Period-r13 ENUMERATED{ms40, ms80, ms160, ms320, ms640}, rmtc-SubframeOffset-r13INTEGER(0..639) OPTIONAL, -- Need ON measDuration-r13 ENUMERATED {sym1,sym14, sym28, sym42, sym70}, ... } } -- ASN1STOP

Particular challenges related to cell quality derivation, beammeasurement information reporting, and measurement object updatecurrently exist in LTE. NR differs from LTE in that for NR thederivation of cell measurement results is quite configurable, at leastbecause of the following reasons. In NR, a cell may transmit multiplebeams pointing in different directions. Because the RS used for cellquality derivation is beamformed, the UE can detect multiple beams foreach cell and therefore needs to combine the beam results to derive cellmeasurements. In addition, NR may configure two different RS types(e.g., SS/PBCH Blocks or CSI-RS). For example, the network may, inreportConfig, configure a UE to either trigger events based on cellmeasurements based on SS/PBCH blocks or CSI-RS.

In NR, a UE may derive cell quality by averaging the best beam with theup to N−1 best beams above a configured absolute threshold. Cell-levelRSRQ is derived by averaging beam RSRQ measurements. The averaging isdone on linear domain. NR also includes RS-SINR based on SS/PBCH blockand CSI-RS for L3 mobility. It may be used for triggering Ax events andreporting. Cell-level RS-SINR is derived in the same way as other cellquantities. The averaging is performed by averaging beam RS-SINRmeasurements, and the averaging is done on linear domain. Independent Nand independent threshold may be configured per carrier frequency in theMeasObject for NR-SS based and CSI-RS based L3 mobility.

The network may configure one or more of the following parameters: (a) athreshold for selecting additional beams for averaging for measurementsbased on SS/PBCH blocks; (b) a threshold for selecting additional beamsfor averaging for measurements based on CSI-RS; (c) N parameter for themaximum number of beams to be averaged for cell measurement resultsbased on SS/PBCH blocks; and (d) N parameter for the maximum number ofbeams to be averaged for cell measurement results based on CSI-RS;

A NR network may request that a UE report beam measurements associatedwith a given cell that has triggered measurement events (e.g., A1-A6). Ameasurement report may include beam measurements (based on NR-SS andCSI-RS). Then network may configure the beam measurement (e.g., thenetwork configures a UE to report beam identifier only, beam measurementresult and identifier, or no beam reporting). The network may configuremeasurement quantities for beam measurement reporting. For selection ofx SS blocks to be included in the measurement report for each cell, thenetwork may configure x separately from N (N used in cell qualityderivation). For cell events (A1 to A6 events), selection of y CSI-RSresource to be included in the measurement report for each cell, thenetwork may configure y separately from N (N used in cell qualityderivation)

For measurement events based on NR-SS, in each cell a UE reports thebest SS block and up to x−1 next highest measured SS blocks above theabsolute threshold. The threshold is the same as that used for cellquality derivation. For measurement events based on CSI-RS, in each cella UE reports the best CSI-RS and up to y−1 next highest measured CSI-RSabove the absolute threshold. The threshold is the same as that used forcell quality derivation.

The parameter N for cell quality derivation (CQD), to be configured perRS type in the measObject, does not affect the way the UE performs beammeasurement results to be included in measurement reports. A newparameter X is defined in reportConfig. The threshold for the selectionof X−1 beams in addition to the best is the same configured in themeasurement object.

The following ASN.1 structures describe the NR measurement object andreportConfig in NR (the excerpt includes a subset of the parameters).

The IE MeasObjectNR specifies information applicable for SS/PBCHblock(s) intra/inter-frequency measurements or CSI-RSintra/inter-frequency measurements.

MeasObjectNR information element -- ASN1START --TAG-MEAS-OBJECT-NR-START MeasObjectNR ::= SEQUENCE { carrierFreq ARFCN-ValueNR, . . . --Consolidation of L1 measurements per RS indexabsoluteThresholdCellQuality SEQUENCE { absThreshSS-BlocksConsolidationThresholdNR OPTIONAL, absThreshCSI-RS-Consolidation ThresholdNR OPTIONAL} OPTIONAL, --Config for cell measurement derivation maxBeamsCellQualitySEQUENCE { nroSS-BlocksToAverage INTEGER (1..maxNroSS-BlocksToAverage)OPTIONAL, nroCSI-RS-ResourcesToAverage INTEGER(1..maxNroCSI-RS-ResourcesToAverage) OPTIONAL } . . . . }Q-OffsetRangeList ::= SEQUENCE { rsrpOffsetSSB Q-OffsetRange DEFAULTdB0, rsrqOffsetSSB Q-OffsetRange DEFAULT dB0, sinrOffsetSSBQ-OffsetRange DEFAULT dB0, rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0,rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0, sinrOffsetCSI-RSQ-OffsetRange DEFAULT dB0 } . . . -- TAG-MEAS-OBJECT-NR-STOP -- ASN1STOP

The nroCSI-RS-ResourcesToAvgWithBest indicates the maximum number ofmeasurement results per CSI-RS resources from the L1 filter(s) to beaveraged with the highest measurement result from the L1 filter(s). Thesame value applies for each detected cell in that carrierFreq.

The nroSS-BlocksToAvgWithBest indicates the maximum number ofmeasurement results per SS/PBCH index from the L1 filter(s) to beaveraged with the highest measurement result from the L1 filter(s). Thesame value applies for each detected cell in that carrierFreq.

The absThreshCSI-RS-Consolidation is the absolute threshold for theconsolidation of measurement results per CSI-RS resource(s) from L1filter(s). The values above the threshold are used as input to thederivation of cell measurement results and the L3 filter(s) per CSI-RSresource.

The absThreshSS-BlocksConsolidation is the absolute threshold for theconsolidation of measurement results per SS/PBCH block(s) from L1filter(s). The values above the threshold are used as input to thederivation of cell measurement results and the L3 filter(s) per SS/PBCHblock index.

The IE ReportConfigNR specifies criteria for triggering of an NRmeasurement reporting event. Measurement reporting events are based oncell measurement results, which can be derived based on SS/PBCH block orCSI-RS. The events are labelled AN with N equal to 1, 2 and so on.

Event A1: Serving becomes better than absolute threshold.

Event A2: Serving becomes worse than absolute threshold.

Event A3: Neighbour becomes amount of offset better than PCell/PSCell.

Event A4: Neighbour becomes better than absolute threshold.

Event A5: PCell/PSCell becomes worse than absolute threshold) ANDNeighbour becomes better than another absolute threshold2.

Event A6: Neighbour becomes amount of offset better than SCell.

ReportConfigNR information element -- ASN1START --TAG-REPORT-CONFIG-START ReportConfigNR ::= SEQUENCE { reportType CHOICE{ periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig,reportCGI Type_FFS!, ... } } -- Current structure allows easierdefinition of new events and new report types e.g. CGI, etc.EventTriggerConfig::= SEQUENCE { eventId CHOICE { event A1 SEQUENCE {a1-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger }, eventA2 SEQUENCE {a2-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger }, eventA3 SEQUENCE { a3-OffsetMeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis,timeToTrigger TimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL },eventA4 SEQUENCE { a4-Threshold MeasTriggerQuantity, reportOnLeaveBOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger,useWhiteCellList BOOLEAN OPTIONAL }, eventA5 SEQUENCE { a5-Threshold1MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, reportOnLeaveBOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger,useWhiteCellList BOOLEAN OPTIONAL }, eventA6 SEQUENCE { a6-OffsetMeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis,timeToTrigger TimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, },rsType SEQUENCE { ss BOOLEAN, csi-rs BOOLEAN } -- Common reportingconfig (at least to periodical and eventTriggered) reportIntervalReportInterval, reportAmount ENUMERATED {FFS!}, -- Cell reportingconfiguration reportQuantityCell MeasReportQuantity, maxReportCellsINTEGER (1..maxCellReport), -- RS index reporting configurationreportQuantityRsIndexes MeasReportQuantityIndexes OPTIONAL,maxNroIndexToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL, -- Ifconfigured the UE includes the best neighbor cells per serving frequencyreportAddNeighMeas TYPE_FFS! } PeriodicalReportConfig ::= SEQUENCE {rsType SEQUENCE { ssb BOOLEAN, csi-rs BOOLEAN } -- Common reportingconfig (at least to periodical and eventTriggered) reportIntervalReportInterval, reportAmount ENUMERATED {FFS!}, -- Cell reportingconfiguration reportQuantityCell MeasReportQuantity, maxReportCellsINTEGER (1..maxCellReport), -- RS index reporting configurationreportQuantityRsIndexes MeasReportQuantityIndexes,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) }MeasTriggerQuantity ::= SEQUENCE { rsrp RSRPRange, rsrq RSRQRange, sinrSINRRange } MeasTriggerQuantityOffset::= SEQUENCE { rsrp INTEGER (FFS!)OPTIONAL, rsrq INTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity ::= SEQUENCE { ss-rsrp BOOLEAN OPTIONAL, ss-rsrqBOOLEAN OPTIONAL, ss-sinr BOOLEAN OPTIONAL, csi-rs-rsrp BOOLEANOPTIONAL, csi-rs-rsrq BOOLEAN OPTIONAL, csi-rs-sinr BOOLEAN OPTIONAL }MeasReportQuantityIndexes::= CHOICE { ss-Indexes BOOLEAN, csi-IndexesBOOLEAN, measResultsPerIndex MeasReportQuantity } --TAG-REPORT-CONFIG-START -- ASN1STOP The IE MeasIdToAddModList includes alist of measurement identities to add or modify and, for each measId, anassociated measObjectId and associated reportConfigId. MeasIdToAddModList information element -- ASN1START --TAG-MEAS-ID-TO-ADD-MOD-LIST-START MeasIdToAddModList ::= SEQUENCE (SIZE(1..maxMeasId)) OF MeasIdToAddMod MeasIdToAddMod ::= SEQUENCE { measIdMeasId, measObjectId MeasObjectId OPTIONAL, reportConfigIdReportConfigId } -- TAG-MEAS-ID-TO-ADD-MOD-LIST-STOP -- ASN1STOP

In LTE, when the measurement object is updated, a UE resets allmeasurement related timers and variables and discards measurementsassociated to the measurement object to be updated. The procedure isdescribed in 36.331 and is reproduced above.

SUMMARY

Based on the description above, certain challenges currently exist. Forexample, current user equipment (UE) behavior when the network triggersa measurement update procedure in fifth generation (5G) new radio (NR)is that the NR parameters configured in the measurement object were notdefined in long term evolution (LTE) and UE actions upon there-configuration of the new parameters is unknown. Resetting allmeasurements and related information may not be necessary for particularupdates.

Particular embodiments may provide solutions to these or otherchallenges. For example, certain embodiments include a method where theUE discards or stores existing measurement information (for beam(s),cell(s), RS type(s), bandwidth parts) and resets timers and measurementrelated UE variables depending on the parameters (or combinations ofparameters) provided by the network when updating cell qualityderivation parameters or beam consolidation parameters. Particularembodiments include UE actions upon reconfiguring cell qualityderivation (CQD) parameters and beam measurement consolidationparameters in terms of storing or removing cell/beam measurements,possibly per RS type, when certain parameters are updated or not for thesame measurement object linked to configured measurements.

According to some embodiments, a method performed by a wireless devicefor updating measurement configuration comprises receiving a measurementconfiguration from a network node. The measurement configurationcomprises a measurement object that includes at least one CQD parameter.The wireless device has previously stored measurement results associatedwith the measurement object. The method further comprises:

determining the measurement object includes a reconfigured CQD parameterthat changes the way the wireless device determines the quality of acell; determining a portion of the previously stored measurement resultswere computed based on the reconfigured CQD parameter; and removing theportion of the previously stored measurement results. The method mayfurther comprise resetting timers and removing measurement informationassociated with the removed measurement results.

In particular embodiments, the measurement object includes a first CQDparameter indicating a maximum number of beams to average for cellmeasurement results and a second CQD parameter indicating a signalquality threshold for selecting additional beams to average for cellmeasurement results. Determining the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell comprises determining the measurementobject includes at least one of the first CQD parameter and the secondCQD parameter, or determining at least one of the first CQD parameterand the second CQD parameter is changed.

In particular embodiments, determining the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell comprises determining: the firstparameter is changed; or the second parameter is changed, and the firstparameter is changed to a value greater than one or the first parameterwas not changed but was greater than one before receiving themeasurement configuration.

In particular embodiments, the first CQD parameter comprises a maximumnumber of beams to average for cell measurements based on a channelstate information reference signal (CSI-RS) and the second CQD parametercomprises a signal quality threshold for selecting additional beams toaverage based on a CSI-RS, or the first CQD parameter comprises amaximum number of beams to average for cell measurements based on asynchronization symbol (SS) and the second CQD parameter comprises asignal quality threshold for selecting additional beams to average basedon a SS.

In particular embodiments, the measurement configuration furthercomprises a report configuration associated with the measurement object.The report configuration comprises an indication of a reference signaltype (e.g., CSI-RS or SS). Determining the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell further comprises determining that thefirst CQD parameter and the second CQD parameter are based on CSI-RS andthe reference signal type is CSI-RS, or determining that the first CQDparameter and the second CQD parameter are based on SS and the referencesignal type is SS.

According to some embodiments, a wireless device is operable to update ameasurement configuration. The wireless device comprises processingcircuitry operable to receive a measurement configuration from a networknode. The measurement configuration comprises a measurement object thatincludes at least one CQD parameter. The wireless device has previouslystored measurement results associated with the measurement object.

The processing circuitry is further operable to: determine themeasurement object includes a reconfigured CQD parameter that changesthe way the wireless device determines the quality of a cell; determinea portion of the previously stored measurement results were computedbased on the reconfigured CQD parameter; and remove the portion of thepreviously stored measurement results. The processing circuitry may befurther operable to reset timers and remove measurement informationassociated with the removed measurement results.

In particular embodiments, the measurement object includes a first CQDparameter indicating a maximum number of beams to average for cellmeasurement results and a second CQD parameter indicating a signalquality threshold for selecting additional beams to average for cellmeasurement results. The processing circuitry is operable to determinethe measurement object includes a reconfigured parameter that changesthe way the wireless device determines the quality of a cell bydetermining the measurement object includes at least one of the firstCQD parameter and the second CQD parameter, or determining at least oneof the first CQD parameter and the second CQD parameter is changed.

In particular embodiments, the processing circuitry is operable todetermine the measurement object includes a reconfigured parameter thatchanges the way the wireless device determines the quality of a cell bydetermining: the first parameter is changed; or the second parameter ischanged, and the first parameter is changed to a value greater than oneor the first parameter was not changed but was greater than one beforereceiving the measurement configuration.

In particular embodiments, the first CQD parameter comprises a maximumnumber of beams to average for cell measurements based on a CSI-RS andthe second CQD parameter comprises a signal quality threshold forselecting additional beams to average based on a CSI-RS; or the firstCQD parameter comprises a maximum number of beams to average for cellmeasurements based on a synchronization symbol (SS) and the second CQDparameter comprises a signal quality threshold for selecting additionalbeams to average based on a SS.

In particular embodiments, the measurement configuration furthercomprises a report configuration associated with the measurement object.The report configuration comprises an indication of a reference signaltype (e.g., CSI-RS or SS). The processing circuitry is operable todetermine the measurement object includes a reconfigured parameter thatchanges the way the wireless device determines the quality of a cell bydetermining that the first CQD parameter and the second CQD parameterare based on CSI-RS and the reference signal type is CSI-RS, ordetermining that the first CQD parameter and the second CQD parameterare based on SS and the reference signal type is SS.

According to some embodiments, a method performed by a wireless devicefor updating measurement configuration comprises receiving a measurementconfiguration from a network node. The measurement configurationcomprises a measurement object that includes at least one CQD parameter.The wireless device has previously stored measurement results associatedwith the measurement object. The method further comprises: determiningthe measurement object includes a reconfigured CQD parameter thatchanges the way the wireless device performs beam measurements orselects beam measurements for reporting; determining a portion of thepreviously stored measurement results were computed based on thereconfigured CQD parameter; and removing the portion of the previouslystored measurement results. The method may further comprise resettingtimers and removing measurement information associated with the removedmeasurement results.

In particular embodiments, the CQD parameter comprises a signal qualitythreshold for selecting additional beams to average for cell measurementresults. Determining the measurement object includes a reconfiguredparameter that changes the way the wireless device performs beammeasurements or selects beam measurements for reporting comprisesdetermining the measurement object includes the CQD parameter, ordetermining the CQD parameter is changed.

In particular embodiments, the CQD parameter comprises a signal qualitythreshold for selecting additional beams to average based on a CSI-RS ora signal quality threshold for selecting additional beams to averagebased on a SS.

In particular embodiments, the measurement configuration furthercomprises a report configuration associated with the measurement object.The report configuration comprises an indication of a reference signaltype (e.g., CSI-RS or SS). Determining the measurement object includes areconfigured parameter that changes the way the wireless device performsbeam measurements or selects beam measurements for reporting furthercomprises determining that the CQD parameter is based on CSI-RS and thereference signal type is CSI-RS, or determining that the CQD parameteris based on SS and the reference signal type is SS.

According to some embodiments, a wireless device is operable to update ameasurement configuration. The wireless device comprises processingcircuitry operable to receive a measurement configuration from a networknode. The measurement configuration comprises a measurement object thatincludes at least one CQD parameter. The processing circuitry is furtheroperable to determine the measurement object includes a reconfigured CQDparameter that changes the way the wireless device performs beammeasurements or selects beam measurements for reporting; determine aportion of the previously stored measurement results were computed basedon the reconfigured CQD parameter; and remove the portion of thepreviously stored measurement results. The processing circuitry may befurther operable to reset timers and remove measurement informationassociated with the removed measurement results.

In particular embodiments, the CQD parameter comprises a signal qualitythreshold for selecting additional beams to average for cell measurementresults. The processing circuitry is operable to determine themeasurement object includes a reconfigured parameter that changes theway the wireless device performs beam measurements or selects beammeasurements for reporting by determining the measurement objectincludes the CQD, or determining the CQD parameter is changed.

In particular embodiments, the CQD parameter comprises a signal qualitythreshold for selecting additional beams to average based on a CSI-RS ora signal quality threshold for selecting additional beams to averagebased on a SS.

In particular embodiments, the measurement configuration furthercomprises a report configuration associated with the measurement object.The report configuration comprises an indication of a reference signaltype (e.g., CSI-RS or SS). The processing circuitry is operable todetermine the measurement object includes a reconfigured parameter thatchanges the way the wireless device performs beam measurements orselects beam measurements for reporting by determining that the CQDparameter is based on CSI-RS and the reference signal type is CSI-RS, ordetermining that the CQD parameter is based on SS and the referencesignal type is SS.

According to some embodiments, a wireless device is operable to update ameasurement configuration. The wireless device comprises a receivingunit, a determining unit, and a removing unit. The receiving unit isoperable to receive a measurement configuration from a network node. Themeasurement configuration comprises a measurement object that includesat least one CQD parameter. The wireless device has previously storedmeasurement results associated with the measurement object. Thedetermining unit is operable to determine the measurement objectincludes a reconfigured CQD parameter that changes the way the wirelessdevice determines the quality of a cell, and determine a portion of thepreviously stored measurement results were computed based on thereconfigured CQD parameter. The removing unit is operable to remove theportion of the previously stored measurement results.

According to some embodiments, a wireless device is operable to update ameasurement configuration. The wireless device comprises a receivingunit, a determining unit, and a removing unit. The receiving unit isoperable to receive a measurement configuration from a network node. Themeasurement configuration comprises a measurement object that includesat least one CQD parameter. The wireless device has previously storedmeasurement results associated with the measurement object. Thedetermining unit is operable to determine the measurement objectincludes a reconfigured CQD parameter that changes the way the wirelessdevice performs beam measurements or selects beam measurements forreporting, and determine a portion of the previously stored measurementresults were computed based on the reconfigured CQD parameter. Theremoving unit is operable to remove the portion of the previously storedmeasurement results.

Also disclosed is a computer program product comprising a non-transitorycomputer readable medium storing computer readable program code, thecomputer readable program code operable, when executed by processingcircuitry to perform any of the methods performed by the wireless devicedescribed above.

Certain embodiments may provide one or more of the following technicaladvantages. For example, the UE does not need to unnecessarily discardpreviously performed measurements when cell quality derivation or beamconsolidation parameters are being updated.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and theirfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a block diagram illustrating an example wireless network;

FIG. 2 illustrates an example user equipment, according to certainembodiments;

FIG. 3 is flowchart illustrating an example method in a wireless devicefor updating measurement configuration, according to certainembodiments;

FIG. 4 is a flowchart illustrating another example method in a wirelessdevice for updating measurement configuration, according to certainembodiments;

FIG. 5 illustrates a schematic block diagram of an apparatus in awireless network, according to certain embodiments;

FIG. 6 illustrates an example virtualization environment, according tocertain embodiments;

FIG. 7 illustrates an example telecommunication network connected via anintermediate network to a host computer, according to certainembodiments;

FIG. 8 illustrates an example host computer communicating via a basestation with a user equipment over a partially wireless connection,according to certain embodiments;

FIG. 9 is a flowchart illustrating a method implemented, according tocertain embodiments;

FIG. 10 is a flowchart illustrating a method implemented in acommunication system, according to certain embodiments;

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, according to certain embodiments; and

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, according to certain embodiments.

DETAILED DESCRIPTION

As described above, certain challenges currently exist with updatingmeasurement configurations in fifth generation (5G) new radio (NR). Forexample, NR includes additional configuration parameters that increasethe complexity of the measurement object. Resetting all measurements andrelated information may not be necessary when only certain parametersare updated.

Particular embodiments may provide solutions to these or otherchallenges. For example, certain embodiments include a method where theUE discards or stores existing measurement information (for beam(s),cell(s), RS type(s), bandwidth parts) and resets timers and measurementrelated UE variables depending on the parameters (or combinations ofparameters) provided by the network when updating cell qualityderivation parameters or beam consolidation parameters.

Particular embodiments are described more fully with reference to theaccompanying drawings. Other embodiments, however, are contained withinthe scope of the subject matter disclosed herein, the disclosed subjectmatter should not be construed as limited to only the embodiments setforth herein; rather, these embodiments are provided by way of exampleto convey the scope of the subject matter to those skilled in the art.

Existing measurement information may include beam measurementinformation and cell measurement information. Beam measurementinformation may include measurement results per SS/PBCH block, such asSS-RSRP, SS-RSRQ, SS-SINR, and measurement results per CSI-RS resource,such as CSI-RSRP, CSI-RSRQ and CSI-SINR. Beam measurements may alsoinclude CSI-RS resource measurement identifiers, and SS/PBCH block(s)indexes. Cell measurement information may include measurement resultsper cell based on SS/PBCH block(s) and measurement results per cellbased on CSI-RS resource(s).

Cell quality derivation (CQD) parameters and beam consolidationparameters may include the following parameters. A Threshold(SSB)parameter is used for selecting additional beams for averaging formeasurements based on SS/PBCH blocks. The same threshold may also beused to select additional beams to be L3 filtered and to be included inmeasurement reports. Thus, Threshold(SSB) may be referred to as a CQDand a beam consolidation parameter. ASN.1 notation may refer to theparameter as absThreshSS-BlocksConsolidation. In some embodiments, L3filters may be disabled in another action.

A Threshold(CSI-RS) parameter is used for selecting additional beams foraveraging for measurements based on CSI-RS. The same threshold may alsobe used to select additional beams to be L3 filtered and to be includedin measurement reports. Thus, the Threshold(CSI-RS) parameter may bereferred to as a CQD and a beam consolidation parameter. ASN.1 notationmay refer to the parameter as absThreshCSI-RS-Consolidation.

A N(SSB) parameter is used for the maximum number of beams to beaveraged for cell measurement results based on SS/PBCH blocks. Theparameter does not affect the L3 filtered beam measurements to beincluded in measurement report. Thus, the parameter may be referred toas a purely CQD parameter. ASN.1 notation may refer to the parameter asnroSS-BlocksToAverage.

A N(CSI-RS) parameter is used for the maximum number of beams to beaveraged for cell measurement results based on CSI-RS. The parameterdoes not affect the L3 filtered beam measurements to be included inmeasurement report. Thus, the parameter may be referred to as a purelyCQD parameter. ASN.1 notation may refer to the parameter asnroCSI-RS-ResourcesToAverage.

In particular embodiments, a UE may perform the following actions uponreceiving a re-configuration of CQD or beam consolidation parameters.For cell measurement results, The UE evaluates whether the update ofcell quality derivation parameters or beam consolidation parametersleads to changes in the way the cell quality is derived. If updates leadto changes in CQD, the UE deletes cell measurement results associated tothe modified measurement object. The criteria to determine whether theupdates lead to changes in CQD may be any of the following: (a) N ischanged (or is configured/re-configured), regardless if theconsolidation threshold is changed (or is configured/re-configured); (b)the consolidation threshold is changed (or is configured/re-configured),and N is changed to a value greater than 1; and/or (c) the consolidationthreshold is changed (or is configured/re-configured), and N is notchanged but its value is already greater than 1 before there-configuration.

Otherwise, if updates dot not lead to changes in CQD, the UE may notdelete cell measurement results associated to the modified measurementobject. The criteria to define whether the updates do not lead tochanges in CQD may be any of the following: (a) N is not changed and theconsolidation threshold is not changed (or none isconfigured/re-configured); and/or (b) the consolidation threshold ischanged, and N is not changed and its value is 1.

For beam measurement results, the UE determines whether the update ofCQD or beam consolidation parameters lead to changes in the way beammeasurements or the selection of beam measurements for measurementreporting are performed. If updates lead to changes in beam measurementsor the selection of beam measurements for measurement reporting, the UEmay delete beam measurement results associated to the modifiedmeasurement object. Criteria for whether the updates lead to changes inbeam measurement or the selection of beam measurement for measurementreporting may be that the consolidation threshold is changed (or isconfigured/re-configured), regardless whether N is changed or not.

Otherwise, if updates dot not lead to changes in beam measurements orthe selection of beam measurements for measurement reporting, the UE maynot delete beam measurement results associated to the modifiedmeasurement object. Criteria for whether the updates lead to changes inbeam measurement or the selection of beam measurement for measurementreporting may be that the consolidation threshold is not changed (or isnot configured/re-configured).

Beam measurement results and cell measurement results can be derivedbased on different RS types (e.g., SS Block and CSI-RS in NR dependingon network configuration. A UE may perform measurement related actions(storing/deleting, etc.) upon the update of CQD or beam consolidationparameters independently for each RS type.

If the updated parameters are associated to SSB related parameters inthe modified measurement object, the UE may consider the previouslydescribed UE actions only for the measurements (i.e., for themeasurement identifiers) associated to reporting configuration whose RStype is set to SSB. If the updated parameters are associated to CSI-RSin the modified measurement object, the UE may consider the previouslydescribed UE actions only for the measurements associated to reportingconfiguration whose RS type is set to CSI-RS.

For a given RS type (i.e., CSI-RS or SS/PBCH block) the updates of oneRS may not affect the measurement associated to the other RS type. Thefollowing table describes whether the re-configuration of CQD and beamconsolidation parameters affect the CQD or beam consolidation for L3beam measurement for reporting.

N Threshold not modified Threshold modified N is not updated UE can keepcell UE can keep cell (and N = 1 in measurements in measurements inVarMeasConfig) VarListMeasResults VarListMeasResults UE can keep beam UEremoves beam measurements in measurements from VarListMeasResultsVarListMeasResults N is not updated UE can keep cell UE removes cell(and N > 1 in measurements in measurements and beam VarMeasConfig)VarListMeasResults measurements from UE can keep beam VarListMeasResultsmeasurements in VarListMeasResults N is updated UE removes cell UEremoves cell measurements and beam measurements and beam measurementsmeasurements in UE can keep beam VarListMeasResults from measurements inVarListMeasResults VarListMeasResults

Particular embodiments include measurement related UE variables and/ortimers and/or counters. When a UE removes the cell measurement resultsaccording to the previously defined rules, the UE may also perform oneor more of the following actions: (a) remove the measurement reportingentry for the measId from the VarMeasReportList, if included; (b) stopthe periodical reporting timer and reset the associated information(e.g., timeToTrigger) for the measId; and/or (c) stop performing L3 beamfiltered measurement results (i.e., release memory associated with L3filters). In some embodiments, the UE receives a re-configuration of CQDparameters and beam measurements for reporting associated to SS/PBCHblocks only and does not delete measurements associated to CSI-RS, orvice versa.

In particular embodiments, the network may update the UE with cellquality derivation parameters or beam consolidation parameters over anRRC message using a measurement configuration procedure, or, moreprecisely, a measurement object update. The method could be written asfollows in the RRC specifications depending on the level of details fromthe proposed method that are specified.

In some embodiments, the UE actions are based on the RS type, configuredvalues, absence of new configuration, etc., as follows:

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                cellsToRemoveList, blackCellsToRemoveList,                whiteCellsToRemoveList, referenceSignalConfig, absolute                ThresholdCellQuality, maxBeamsCellQuality;    -   . . . (other actions)        -   for each measId associated with this measObjectId in the            measIdList within the VarMeasConfig, if any            -   if the received measObject includes the                absThreshSS-BlocksConsolidation different from the value                in VarMeasConfig for the same measObject:                -   if the received measObject includes the                    nroSS-BlocksToAverage different from the value in                    VarMeasConfig for the same measObject or,                -   if the nroSS-BlocksToAverage in VarMeasConfig for                    the same measObject is greater than one:                -    if the rsType in the reportConfig associated to                    that measId is set to ssb:                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if included;                -    stop the periodical reporting timer and reset the                    associated information (e.g., timeToTrigger) for                    this measId;                -    else,                -    remove beam measurements based on SS/PBCH block                    associated to the measurement reporting entry for                    this measId from the VarMeasReportList, if included;            -   if the received measObject includes the                absThreshCSI-RS-Consolidation different from the value                in VarMeasConfig for the same measObject:                -   if the received measObject includes the                    nroCSI-RS-ResourcesToAverage different from the                    value in VarMeasConfig for the same measObject or,                -   if the nroCSI-RS-ResourcesToAverage in VarMeasConfig                    for the same measObject is greater than one:                -    if the rsType in the reportConfig associated to                    that measId is set to csi-rs:                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if included;                -    stop the periodical reporting timer and reset the                    associated information (e.g. timeToTrigger) for this                    measId;                -    else,                -    remove beam measurements based on CSI-RS associated                    to the measurement reporting entry for this measId                    from the VarMeasReportList, if included;    -   else:        -   add a new entry for the received measObject to the            measObjectList within VarMeasConfig.

In some embodiments, the UE actions may be based on the RS type,regardless of the type of thresholds and other parameters configured, asfollows:

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                cellsToRemoveList, blackCellsToRemoveList,                whiteCellsToRemoveList, referenceSignalConfig,                absoluteThresholdCellQuality, maxBeamsCellQuality;    -   . . . (other actions)        -   for each measId associated with this measObjectId in the            measIdList within the VarMeasConfig, if any            -   if the received measObject includes the                absThreshSS-BlocksConsolidation different from the value                in VarMeasConfig for the same measObject or,            -   if the received measObject includes the                nroSS-BlocksToAverage different from the value in                VarMeasConfig for the same measObject:                -   if the rsType in the reportConfig associated to that                    measId is set to ssb                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if include;                -    stop the periodical reporting timer and reset the                    associated information (e.g., timeToTrigger) for                    this measId;            -   if the received measObject includes the                absThreshCSI-RS-Consolidation different from the value                in VarMeasConfig for the same measObject or,            -   if the received measObject includes the                nroCSI-RS-ResourcesToAverage different from the value in                VarMeasConfig for the same measObject:                -   if the rsType in the reportConfig associated to that                    measId is set to csi-rs                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if included;                -    stop the periodical reporting timer and reset the                    associated information (e.g. timeToTrigger) for this                    measId;        -   else:            -   add a new entry for the received measObject to the                measObjectList within VarMeasConfig.

In some embodiments, the UE actions may be based on the RS type as longas parameters associated to a given thresholds are included in theupdated measurement object, regardless if the values differ frompreviously configured values, as follows:

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                cellsToRemoveList, blackCellsToRemoveList,                whiteCellsToRemoveList, referenceSignalConfig,                absoluteThresholdCellQuality, maxBeamsCellQuality;    -   . . . (other actions)        -   for each measId associated with this measObjectId in the            measIdList within the VarMeasConfig, if any            -   if the received measObject includes the                absThreshSS-BlocksConsolidation or,            -   if the received measObject includes the                nroSS-BlocksToAverage:                -   if the rsType in the reportConfig associated to that                    measId is set to ssb                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if include;                -    stop the periodical reporting timer and reset the                    associated information (e.g., timeToTrigger) for                    this measId;                -   if the received measObject includes the                    absThreshCSI-RS-Consolidation or,                -   if the received measObject includes the                    nroCSI-RS-ResourcesToAverage:                -    if the rsType in the reportConfig associated to                    that measId is set to csi-rs                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if included;                -    stop the periodical reporting timer and reset the                    associated information (e.g. timeToTrigger) for this                    measId;        -   else:            -   add a new entry for the received measObject to the                measObjectList within VarMeasConfig.

In some embodiments, the UE actions may be as follows:

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                cellsToRemoveList, blackCellsToRemoveList,                whiteCellsToRemoveList, referenceSignalConfig,                absoluteThresholdCellQuality, maxBeamsCellQuality;    -   . . . (other actions)        -   for each measId associated with this measObjectId in the            measIdList within the VarMeasConfig, if any            -   if the received measObject includes the                absThreshSS-BlocksConsolidation or,            -   if the received measObject includes the                nroSS-BlocksToAverage different from the value in                VarMeasConfig for the same measObject:                -   if the rsType in the reportConfig associated to that                    measId is set to ssb                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if include;                -    stop the periodical reporting timer and reset the                    associated information (e.g., time ToTrigger) for                    this measId;            -   if the received measObject includes the                absThreshCSI-RS-Consolidation or,            -   if the received measObject includes the                nroCSI-RS-ResourcesToAverage different from the value in                VarMeasConfig for the same measObject:                -   if the rsType in the reportConfig associated to that                    measId is set to csi-rs                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if included;                -    stop the periodical reporting timer and reset the                    associated information (e.g., timeToTrigger) for                    this measId;        -   else:            -   add a new entry for the received measObject to the                measObjectList within VarMeasConfig.

In some embodiments, the UE actions may be as follows:

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                cellsToRemoveList, blackCellsToRemoveList,                whiteCellsToRemoveList, referenceSignalConfig,                absoluteThresholdCellQuality, maxBeamsCellQuality;    -   . . . (other actions)        -   for each measId associated with this measObjectId in the            measIdList within the VarMeasConfig, if any            -   if the received measObject includes the                absThreshSS-BlocksConsolidation different from the value                in VarMeasConfig for the same measObject or,            -   if the received measObject includes the                nroSS-BlocksToAverage:                -   if the rsType in the reportConfig associated to that                    measId is set to ssb                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if include;                -    stop the periodical reporting timer and reset the                    associated information (e.g., timeToTrigger) for                    this measId;                -   if the received measObject includes the                    absThreshCSI-RS-Consolidation different from the                    value in VarMeasConfig for the same measObject or,                -   if the received measObject includes the                    nroCSI-RS-ResourcesToAverage:                -    if the rsType in the reportConfig associated to                    that measId is set to csi-rs                -    remove the measurement reporting entry for this                    measId from the VarMeasReportList, if included;                -    stop the periodical reporting timer and reset the                    associated information (e.g., timeToTrigger) for                    this measId;    -   else:        -   add a new entry for the received measObject to the            measObjectList within VarMeasConfig.

In some embodiments, the UE actions may be based on the change of anyparameter in the same IE carrying the CQD parameters and beamconsolidation parameters, e.g., modification of a measurement object,regardless of the type of thresholds and other parameters configured,regardless if the values differ from previously configured values, asfollows:

-   -   for each measObjectId included in the received        measObjectToAddModList:        -   if an entry with the matching measObjectId exists in the            measObjectList within the VarMeasConfig, for this entry:            -   reconfigure the entry with the value received for this                measObject, except for the fields cellsToAddModList,                blackCellsToAddModList, whiteCellsToAddModList,                cellsToRemoveList, blackCellsToRemoveList,                whiteCellsToRemoveList, referenceSignalConfig, absolute                ThresholdCellQuality, maxBeamsCellQuality;    -   . . . (other actions)        -   for each measId associated with this measObjectId in the            measIdList within the VarMeasConfig, if any            -   remove the measurement reporting entry for this measId                from the VarMeasReportList, if included            -   stop the periodical reporting timer and reset the                associated information (e.g. timeToTrigger) for this                measId;        -   else:            -   add a new entry for the received measObject to the                measObjectList within VarMeasConfig.

Although the embodiments herein are described with respect to a NRmeasurement object updated from NR RRC, the features, benefits, steps,disclosed herein may also be applied when a UE connected to LTE isconfigured with NR measurement objects and, E-UTRAN reconfigures atleast one NR measurement object. Depending on the parameters that areupdated, the UE can perform any of the actions described in the previousembodiments.

FIG. 1 illustrates an example wireless network, according to certainembodiments. The wireless network may comprise and/or interface with anytype of communication, telecommunication, data, cellular, and/or radionetwork or other similar type of system. In some embodiments, thewireless network may be configured to operate according to specificstandards or other types of predefined rules or procedures. Thus,particular embodiments of the wireless network may implementcommunication standards, such as Global System for Mobile Communications(GSM), Universal Mobile

Telecommunications System (UMTS), Long Term Evolution (LTE), and/orother suitable 2G, 3G, 4G, or 5G standards; wireless local area network(WLAN) standards, such as the IEEE 802.11 standards; and/or any otherappropriate wireless communication standard, such as the WorldwideInteroperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/orZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 160 and WD 110 comprise various components described inmore detail below. These components work together to provide networknode and/or wireless device functionality, such as providing wirelessconnections in a wireless network. In different embodiments, thewireless network may comprise any number of wired or wireless networks,network nodes, base stations, controllers, wireless devices, relaystations, and/or any other components or systems that may facilitate orparticipate in the communication of data and/or signals whether viawired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network.

Examples of network nodes include, but are not limited to, access points(APs) (e.g., radio access points), base stations (BSs) (e.g., radio basestations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Basestations may be categorized based on the amount of coverage they provide(or, stated differently, their transmit power level) and may then alsobe referred to as femto base stations, pico base stations, micro basestations, or macro base stations.

A base station may be a relay node or a relay donor node controlling arelay. A network node may also include one or more (or all) parts of adistributed radio base station such as centralized digital units and/orremote radio units (RRUs), sometimes referred to as Remote Radio Heads(RRHs). Such remote radio units may or may not be integrated with anantenna as an antenna integrated radio. Parts of a distributed radiobase station may also be referred to as nodes in a distributed antennasystem (DAS). Yet further examples of network nodes includemulti-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node asdescribed in more detail below. More generally, however, network nodesmay represent any suitable device (or group of devices) capable,configured, arranged, and/or operable to enable and/or provide awireless device with access to the wireless network or to provide someservice to a wireless device that has accessed the wireless network.

In FIG. 1, network node 160 includes processing circuitry 170, devicereadable medium 180, interface 190, auxiliary equipment 184, powersource 186, power circuitry 187, and antenna 162. Although network node160 illustrated in the example wireless network of FIG. 1 may representa device that includes the illustrated combination of hardwarecomponents, other embodiments may comprise network nodes with differentcombinations of components.

It is to be understood that a network node comprises any suitablecombination of hardware and/or software needed to perform the tasks,features, functions and methods disclosed herein. Moreover, while thecomponents of network node 160 are depicted as single boxes locatedwithin a larger box, or nested within multiple boxes, in practice, anetwork node may comprise multiple different physical components thatmake up a single illustrated component (e.g., device readable medium 180may comprise multiple separate hard drives as well as multiple RAMmodules).

Similarly, network node 160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node.

In some embodiments, network node 160 may be configured to supportmultiple radio access technologies (RATs). In such embodiments, somecomponents may be duplicated (e.g., separate device readable medium 180for the different RATs) and some components may be reused (e.g., thesame antenna 162 may be shared by the RATs). Network node 160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 160.

Processing circuitry 170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 170 may include processing informationobtained by processing circuitry 170 by, for example, converting theobtained information into other information, comparing the obtainedinformation or converted information to information stored in thenetwork node, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Processing circuitry 170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 160 components, such as device readable medium 180, network node160 functionality.

For example, processing circuitry 170 may execute instructions stored indevice readable medium 180 or in memory within processing circuitry 170.Such functionality may include providing any of the various wirelessfeatures, functions, or benefits discussed herein. In some embodiments,processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more ofradio frequency (RF) transceiver circuitry 172 and baseband processingcircuitry 174. In some embodiments, radio frequency (RF) transceivercircuitry 172 and baseband processing circuitry 174 may be on separatechips (or sets of chips), boards, or units, such as radio units anddigital units. In alternative embodiments, part or all of RF transceivercircuitry 172 and baseband processing circuitry 174 may be on the samechip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 170executing instructions stored on device readable medium 180 or memorywithin processing circuitry 170. In alternative embodiments, some or allof the functionality may be provided by processing circuitry 170 withoutexecuting instructions stored on a separate or discrete device readablemedium, such as in a hard-wired manner. In any of those embodiments,whether executing instructions stored on a device readable storagemedium or not, processing circuitry 170 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 170 alone or to other components ofnetwork node 160 but are enjoyed by network node 160 as a whole, and/orby end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 170. Device readable medium 180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 170 and, utilized by network node 160. Devicereadable medium 180 may be used to store any calculations made byprocessing circuitry 170 and/or any data received via interface 190. Insome embodiments, processing circuitry 170 and device readable medium180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication ofsignaling and/or data between network node 160, network 106, and/or WDs110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 tosend and receive data, for example to and from network 106 over a wiredconnection. Interface 190 also includes radio front end circuitry 192that may be coupled to, or in certain embodiments a part of, antenna162.

Radio front end circuitry 192 comprises filters 198 and amplifiers 196.Radio front end circuitry 192 may be connected to antenna 162 andprocessing circuitry 170. Radio front end circuitry may be configured tocondition signals communicated between antenna 162 and processingcircuitry 170. Radio front end circuitry 192 may receive digital datathat is to be sent out to other network nodes or WDs via a wirelessconnection. Radio front end circuitry 192 may convert the digital datainto a radio signal having the appropriate channel and bandwidthparameters using a combination of filters 198 and/or amplifiers 196. Theradio signal may then be transmitted via antenna 162. Similarly, whenreceiving data, antenna 162 may collect radio signals which are thenconverted into digital data by radio front end circuitry 192. Thedigital data may be passed to processing circuitry 170. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

In certain alternative embodiments, network node 160 may not includeseparate radio front end circuitry 192, instead, processing circuitry170 may comprise radio front end circuitry and may be connected toantenna 162 without separate radio front end circuitry 192. Similarly,in some embodiments, all or some of RF transceiver circuitry 172 may beconsidered a part of interface 190. In still other embodiments,interface 190 may include one or more ports or terminals 194, radiofront end circuitry 192, and RF transceiver circuitry 172, as part of aradio unit (not shown), and interface 190 may communicate with basebandprocessing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 162 may becoupled to radio front end circuitry 190 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 162 may comprise one or more omni-directional,sector or panel antennas operable to transmit/receive radio signalsbetween, for example, 2 GHz and 66 GHz. An omni-directional antenna maybe used to transmit/receive radio signals in any direction, a sectorantenna may be used to transmit/receive radio signals from deviceswithin a particular area, and a panel antenna may be a line of sightantenna used to transmit/receive radio signals in a relatively straightline. In some instances, the use of more than one antenna may bereferred to as MIMO. In certain embodiments, antenna 162 may be separatefrom network node 160 and may be connectable to network node 160 throughan interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 162, interface 190, and/or processing circuitry 170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node 160with power for performing the functionality described herein. Powercircuitry 187 may receive power from power source 186. Power source 186and/or power circuitry 187 may be configured to provide power to thevarious components of network node 160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 186 may either be included in,or external to, power circuitry 187 and/or network node 160.

For example, network node 160 may be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 187. As a further example, power source 186 maycomprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 160 may include additionalcomponents beyond those shown in FIG. 1 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 160 may include user interface equipment to allow input ofinformation into network node 160 and to allow output of informationfrom network node 160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air.

In some embodiments, a WD may be configured to transmit and/or receiveinformation without direct human interaction. For instance, a WD may bedesigned to transmit information to a network on a predeterminedschedule, when triggered by an internal or external event, or inresponse to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, amobile phone, a cell phone, a voice over IP (VoIP) phone, a wirelesslocal loop phone, a desktop computer, a personal digital assistant(PDA), a wireless cameras, a gaming console or device, a music storagedevice, a playback appliance, a wearable terminal device, a wirelessendpoint, a mobile station, a tablet, a laptop, a laptop-embeddedequipment (LEE), a laptop-mounted equipment (LME), a smart device, awireless customer-premise equipment (CPE). a vehicle-mounted wirelessterminal device, etc. A WD may support device-to-device (D2D)communication, for example by implementing a 3GPP standard for sidelinkcommunication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure(V2I), vehicle-to-everything (V2X) and may in this case be referred toas a D2D communication device.

As yet another specific example, in an Internet of Things (IoT)scenario, a WD may represent a machine or other device that performsmonitoring and/or measurements and transmits the results of suchmonitoring and/or measurements to another WD and/or a network node. TheWD may in this case be a machine-to-machine (M2M) device, which may in a3GPP context be referred to as an MTC device. As one example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Examples of such machines or devices are sensors, meteringdevices such as power meters, industrial machinery, or home or personalappliances (e.g. refrigerators, televisions, etc.) personal wearables(e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment thatis capable of monitoring and/or reporting on its operational status orother functions associated with its operation. A WD as described abovemay represent the endpoint of a wireless connection, in which case thedevice may be referred to as a wireless terminal. Furthermore, a WD asdescribed above may be mobile, in which case it may also be referred toas a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114,processing circuitry 120, device readable medium 130, user interfaceequipment 132, auxiliary equipment 134, power source 136 and powercircuitry 137. WD 110 may include multiple sets of one or more of theillustrated components for different wireless technologies supported byWD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, orBluetooth wireless technologies, just to mention a few. These wirelesstechnologies may be integrated into the same or different chips or setof chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 114. In certain alternative embodiments, antenna 111 may beseparate from WD 110 and be connectable to WD 110 through an interfaceor port. Antenna 111, interface 114, and/or processing circuitry 120 maybe configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 111 may beconsidered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112and antenna 111. Radio front end circuitry 112 comprise one or morefilters 118 and amplifiers 116. Radio front end circuitry 114 isconnected to antenna 111 and processing circuitry 120 and is configuredto condition signals communicated between antenna 111 and processingcircuitry 120. Radio front end circuitry 112 may be coupled to or a partof antenna 111. In some embodiments, WD 110 may not include separateradio front end circuitry 112; rather, processing circuitry 120 maycomprise radio front end circuitry and may be connected to antenna 111.Similarly, in some embodiments, some or all of RF transceiver circuitry122 may be considered a part of interface 114.

Radio front end circuitry 112 may receive digital data that is to besent out to other network nodes or WDs via a wireless connection. Radiofront end circuitry 112 may convert the digital data into a radio signalhaving the appropriate channel and bandwidth parameters using acombination of filters 118 and/or amplifiers 116. The radio signal maythen be transmitted via antenna 111. Similarly, when receiving data,antenna 111 may collect radio signals which are then converted intodigital data by radio front end circuitry 112. The digital data may bepassed to processing circuitry 120. In other embodiments, the interfacemay comprise different components and/or different combinations ofcomponents.

Processing circuitry 120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 110components, such as device readable medium 130, WD 110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry120 may execute instructions stored in device readable medium 130 or inmemory within processing circuitry 120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 120 includes one or more of RFtransceiver circuitry 122, baseband processing circuitry 124, andapplication processing circuitry 126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry120 of WD 110 may comprise a SOC. In some embodiments, RF transceivercircuitry 122, baseband processing circuitry 124, and applicationprocessing circuitry 126 may be on separate chips or sets of chips.

In alternative embodiments, part or all of baseband processing circuitry124 and application processing circuitry 126 may be combined into onechip or set of chips, and RF transceiver circuitry 122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 122 and baseband processing circuitry124 may be on the same chip or set of chips, and application processingcircuitry 126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 122,baseband processing circuitry 124, and application processing circuitry126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 122 may be a part of interface114. RF transceiver circuitry 122 may condition RF signals forprocessing circuitry 120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 120 executing instructions stored on device readable medium130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner.

In any of those embodiments, whether executing instructions stored on adevice readable storage medium or not, processing circuitry 120 can beconfigured to perform the described functionality. The benefits providedby such functionality are not limited to processing circuitry 120 aloneor to other components of WD 110, but are enjoyed by WD 110, and/or byend users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 120, may include processinginformation obtained by processing circuitry 120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 120. Device readable medium 130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 120. In someembodiments, processing circuitry 120 and device readable medium 130 maybe integrated.

User interface equipment 132 may provide components that allow for ahuman user to interact with WD 110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment132 may be operable to produce output to the user and to allow the userto provide input to WD 110. The type of interaction may vary dependingon the type of user interface equipment 132 installed in WD 110. Forexample, if WD 110 is a smart phone, the interaction may be via a touchscreen; if WD 110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).

User interface equipment 132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 132 is configured to allow input of information into WD 110and is connected to processing circuitry 120 to allow processingcircuitry 120 to process the input information. User interface equipment132 may include, for example, a microphone, a proximity or other sensor,keys/buttons, a touch display, one or more cameras, a USB port, or otherinput circuitry. User interface equipment 132 is also configured toallow output of information from WD 110, and to allow processingcircuitry 120 to output information from WD 110. User interfaceequipment 132 may include, for example, a speaker, a display, vibratingcircuitry, a USB port, a headphone interface, or other output circuitry.Using one or more input and output interfaces, devices, and circuits, ofuser interface equipment 132, WD 110 may communicate with end usersand/or the wireless network and allow them to benefit from thefunctionality described herein.

Auxiliary equipment 134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 110 may further comprise power circuitry 137for delivering power from power source 136 to the various parts of WD110 which need power from power source 136 to carry out anyfunctionality described or indicated herein. Power circuitry 137 may incertain embodiments comprise power management circuitry.

Power circuitry 137 may additionally or alternatively be operable toreceive power from an external power source; in which case WD 110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry 137 may also in certain embodiments be operable todeliver power from an external power source to power source 136. Thismay be, for example, for the charging of power source 136. Powercircuitry 137 may perform any formatting, converting, or othermodification to the power from power source 136 to make the powersuitable for the respective components of WD 110 to which power issupplied.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 1. Forsimplicity, the wireless network of FIG. 1 only depicts network 106,network nodes 160 and 160 b, and WDs 110, 110 b, and 110 c. In practice,a wireless network may further include any additional elements suitableto support communication between wireless devices or between a wirelessdevice and another communication device, such as a landline telephone, aservice provider, or any other network node or end device. Of theillustrated components, network node 160 and wireless device (WD) 110are depicted with additional detail. The wireless network may providecommunication and other types of services to one or more wirelessdevices to facilitate the wireless devices' access to and/or use of theservices provided by, or via, the wireless network.

FIG. 2 illustrates an example user equipment, according to certainembodiments. As used herein, a user equipment or UE may not necessarilyhave a user in the sense of a human user who owns and/or operates therelevant device. Instead, a UE may represent a device that is intendedfor sale to, or operation by, a human user but which may not, or whichmay not initially, be associated with a specific human user (e.g., asmart sprinkler controller). Alternatively, a UE may represent a devicethat is not intended for sale to, or operation by, an end user but whichmay be associated with or operated for the benefit of a user (e.g., asmart power meter). UE 200 may be any UE identified by the 3^(rd)Generation Partnership Project (3GPP), including a NB-IoT UE, a machinetype communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200,as illustrated in FIG. 2, is one example of a WD configured forcommunication in accordance with one or more communication standardspromulgated by the 3^(rd) Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG. 2is a UE, the components discussed herein are equally applicable to a WD,and vice-versa.

In FIG. 2, UE 200 includes processing circuitry 201 that is operativelycoupled to input/output interface 205, radio frequency (RF) interface209, network connection interface 211, memory 215 including randomaccess memory (RAM) 217, read-only memory (ROM) 219, and storage medium221 or the like, communication subsystem 231, power source 233, and/orany other component, or any combination thereof. Storage medium 221includes operating system 223, application program 225, and data 227. Inother embodiments, storage medium 221 may include other similar types ofinformation. Certain UEs may use all the components shown in FIG. 2, oronly a subset of the components. The level of integration between thecomponents may vary from one UE to another UE. Further, certain UEs maycontain multiple instances of a component, such as multiple processors,memories, transceivers, transmitters, receivers, etc.

In FIG. 2, processing circuitry 201 may be configured to processcomputer instructions and data. Processing circuitry 201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configuredto provide a communication interface to an input device, output device,or input and output device. UE 200 may be configured to use an outputdevice via input/output interface 205.

An output device may use the same type of interface port as an inputdevice. For example, a USB port may be used to provide input to andoutput from UE 200. The output device may be a speaker, a sound card, avideo card, a display, a monitor, a printer, an actuator, an emitter, asmartcard, another output device, or any combination thereof.

UE 200 may be configured to use an input device via input/outputinterface 205 to allow a user to capture information into UE 200. Theinput device may include a touch-sensitive or presence-sensitivedisplay, a camera (e.g., a digital camera, a digital video camera, a webcamera, etc.), a microphone, a sensor, a mouse, a trackball, adirectional pad, a trackpad, a scroll wheel, a smartcard, and the like.The presence-sensitive display may include a capacitive or resistivetouch sensor to sense input from a user. A sensor may be, for instance,an accelerometer, a gyroscope, a tilt sensor, a force sensor, amagnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device may bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 2, RF interface 209 may be configured to provide a communicationinterface to RF components such as a transmitter, a receiver, and anantenna. Network connection interface 211 may be configured to provide acommunication interface to network 243 a. Network 243 a may encompasswired and/or wireless networks such as a local-area network (LAN), awide-area network (WAN), a computer network, a wireless network, atelecommunications network, another like network or any combinationthereof. For example, network 243 a may comprise a Wi-Fi network.Network connection interface 211 may be configured to include a receiverand a transmitter interface used to communicate with one or more otherdevices over a communication network according to one or morecommunication protocols, such as Ethernet, TCP/IP, SONET, ATM, or thelike. Network connection interface 211 may implement receiver andtransmitter functionality appropriate to the communication network links(e.g., optical, electrical, and the like). The transmitter and receiverfunctions may share circuit components, software or firmware, oralternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processingcircuitry 201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 219 maybe configured to provide computer instructions or data to processingcircuitry 201. For example, ROM 219 may be configured to store invariantlow-level system code or data for basic system functions such as basicinput and output (I/O), startup, or reception of keystrokes from akeyboard that are stored in a non-volatile memory.

Storage medium 221 may be configured to include memory such as RAM, ROM,programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), electrically erasable programmable read-only memory(EEPROM), magnetic disks, optical disks, floppy disks, hard disks,removable cartridges, or flash drives. In one example, storage medium221 may be configured to include operating system 223, applicationprogram 225 such as a web browser application, a widget or gadget engineor another application, and data file 227. Storage medium 221 may store,for use by UE 200, any of a variety of various operating systems orcombinations of operating systems.

Storage medium 221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 221 may allow UE 200 to access computer-executable instructions,application programs or the like, stored on transitory or non-transitorymemory media, to off-load data, or to upload data. An article ofmanufacture, such as one utilizing a communication system may betangibly embodied in storage medium 221, which may comprise a devicereadable medium.

In FIG. 2, processing circuitry 201 may be configured to communicatewith network 243 b using communication subsystem 231. Network 243 a andnetwork 243 b may be the same network or networks or different networkor networks. Communication subsystem 231 may be configured to includeone or more transceivers used to communicate with network 243 b. Forexample, communication subsystem 231 may be configured to include one ormore transceivers used to communicate with one or more remotetransceivers of another device capable of wireless communication such asanother WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.2,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 233 and/or receiver 235 to implement transmitter orreceiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 233 andreceiver 235 of each transceiver may share circuit components, softwareor firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 200 or partitioned acrossmultiple components of UE 200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem231 may be configured to include any of the components described herein.Further, processing circuitry 201 may be configured to communicate withany of such components over bus 202. In another example, any of suchcomponents may be represented by program instructions stored in memorythat when executed by processing circuitry 201 perform the correspondingfunctions described herein. In another example, the functionality of anyof such components may be partitioned between processing circuitry 201and communication subsystem 231. In another example, thenon-computationally intensive functions of any of such components may beimplemented in software or firmware and the computationally intensivefunctions may be implemented in hardware.

FIG. 3 is a flowchart illustrating an example method in a user equipmentfor updating measurement configuration, according to certainembodiments. In particular embodiments, one or more steps of FIG. 3 maybe performed by wireless device 110 described with respect to FIG. 1.

The method begins at step 3112, where the wireless device (e.g.,wireless device 110) receives a measurement configuration from a networknode (e.g., network node 160). The measurement configuration comprises ameasurement object that includes at least one CQD parameter. Thewireless device has previously stored measurement results associatedwith the measurement object. For example, the CQD parameter may includeone or more of Threshold(SSB), Threshold(CSI-RS), N(SSB), and N(CSI-RS)described above. Some embodiments may include additional parameters thatmay affect how a wireless device determines a cell quality.

At step 3114, the wireless device determines the measurement objectincludes a reconfigured CQD parameter that changes the way the wirelessdevice determines the quality of a cell. For example, wireless device110 may determine the reconfigured CQD parameter changes the way thewireless device determines the quality of a cell based on the presenceof the CQD parameter in the measurement object, based on the CQDparameter changing from a previous value, or based on a combination ofCQD parameters.

In particular embodiments, the measurement object includes a first CQDparameter indicating a maximum number of beams (e.g., N(SSB) orN(CSI-RS)) to average for cell measurement results and a second CQDparameter indicating a signal quality threshold (e.g., Threshold(SSB) orThreshold(CSI-RS)) for selecting additional beams to average for cellmeasurement results. Determining the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell comprises determining the measurementobject includes at least one of the first CQD parameter and the secondCQD parameter, or determining at least one of the first CQD parameterand the second CQD parameter is changed.

In particular embodiments, determining the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell comprises determining: the firstparameter is changed; or the second parameter is changed, and the firstparameter is changed to a value greater than one or the first parameterwas not changed but was greater than one before receiving themeasurement configuration.

In particular embodiments, the measurement configuration furthercomprises a report configuration associated with the measurement object.The report configuration comprises an indication of a reference signaltype (e.g., CSI-RS or SS). Determining the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell further comprises determining that thefirst CQD parameter and the second CQD parameter are based on CSI-RS andthe reference signal type is CSI-RS, or determining that the first CQDparameter and the second CQD parameter are based on SS and the referencesignal type is SS.

At step 316, the wireless device determines a portion of the previouslystored measurement results were computed based on the reconfigured CQDparameter. For example, wireless device 110 may determine itsVarMeasReportList includes a measId of the received measurement objectand that the measurement reporting entry includes measurement resultsbased on the reconfigured CQD parameters. For example, the measurementreporting entry may include both SS and CSI-RS based measurements. Ifthe reconfigured CQD parameter is a CSI-RS parameter, then the wirelessdevice may determine the CSI-RS measurement results are based on theconfigured CQD parameter. In some embodiments, all or none of themeasurements may be based on the reconfigured CQD parameter.

At step 3118, the wireless device removes the portion of the previouslystored measurement results. For example, wireless device 110 may removethe measurements in the VarMeasReportList identified in the previousstep, while keeping other measurements. A particular advantage is thatonly the measurements that depend on the reconfigured CQD parameters areremoved, while other measurements, if any, may be preserved.

The wireless device may also reset timers and remove measurementinformation associated with the removed measurement results. Forexample, wireless device 110 may stop a periodical reporting timer andreset associated information (e.g., timeToTrigger).

Modifications, additions, or omissions may be made to method 3100 ofFIG. 3. Additionally, one or more steps in the method of FIG. 3 may beperformed in parallel or in any suitable order.

FIG. 4 is a flowchart illustrating another example method in a wirelessdevice for updating measurement configuration, according to certainembodiments. In particular embodiments, one or more steps of FIG. 4 maybe performed by network node 160 described with respect to FIG. 1.

The method begins at step 4112, where the wireless device (e.g.,wireless device 110) receives a measurement configuration from a networknode (e.g., network node 160). The measurement configuration comprises ameasurement object that includes at least one CQD parameter. Thewireless device has previously stored measurement results associatedwith the measurement object. For example, the CQD parameter may includeone or more of Threshold(SSB), Threshold(CSI-RS), N(SSB), and N(CSI-RS)described above. Some embodiments may include additional parameters thatmay affect how a wireless device determines a cell quality.

At step 4114, the wireless device determines the measurement objectincludes a reconfigured CQD parameter that changes the way the wirelessdevice performs beam measurements or selects beam measurements forreporting. For example, wireless device 110 may determine thereconfigured CQD parameter changes the way the wireless device performsbeam measurements or selects beam measurements for reporting based onthe presence of the CQD parameter in the measurement object, based onthe CQD parameter changing from a previous value, or based on acombination of CQD parameters.

In particular embodiments, the CQD parameter comprises a signal qualitythreshold (e.g., Threshold(SSB) or Threshold(CSI-RS)) for selectingadditional beams to average for cell measurement results. Determiningthe measurement object includes a reconfigured parameter that changesthe way the wireless device performs beam measurements or selects beammeasurements for reporting comprises determining the measurement objectincludes the CQD parameter, or determining the CQD parameter is changed.

In particular embodiments, the CQD parameter comprises a signal qualitythreshold for selecting additional beams to average based on a CSI-RS ora signal quality threshold for selecting additional beams to averagebased on a SS. The measurement configuration further comprises a reportconfiguration associated with the measurement object. The reportconfiguration comprises an indication of a reference signal type (e.g.,CSI-RS or SS). Determining the measurement object includes areconfigured parameter that changes the way the wireless device performsbeam measurements or selects beam measurements for reporting furthercomprises determining that the CQD parameter is based on CSI-RS and thereference signal type is CSI-RS, or determining that the CQD parameteris based on SS and the reference signal type is SS.

At step 416, the wireless device determines a portion of the previouslystored measurement results were computed based on the reconfigured CQDparameter. For example, wireless device 110 may determine itsVarMeasReportList includes a measId of the received measurement objectand that the measurement reporting entry includes measurement resultsbased on the reconfigured CQD parameters. For example, the measurementreporting entry may include both SS and CSI-RS based measurements. Ifthe reconfigured CQD parameter is a CSI-RS parameter, then the wirelessdevice may determine the CSI-RS measurement results are based on theconfigured CQD parameter. In some embodiments, all or none of themeasurements may be based on the reconfigured CQD parameter.

At step 4118, the wireless device removes the portion of the previouslystored measurement results. For example, wireless device 110 may removethe measurements in the VarMeasReportList identified in the previousstep, while keeping other measurements. A particular advantage is thatonly the measurements that depend on the reconfigured CQD parameters areremoved, while other measurements, if any, may be preserved.

The wireless device may also reset timers and remove measurementinformation associated with the removed measurement results. Forexample, wireless device 110 may stop a periodical reporting timer andreset associated information (e.g., timeToTrigger).

Modifications, additions, or omissions may be made to method 4100 ofFIG. 4. Additionally, one or more steps in the method of FIG. 4 may beperformed in parallel or in any suitable order.

FIG. 5 illustrates a schematic block diagram of an apparatus in awireless network (for example, wireless device 110 of the wirelessnetwork illustrated in FIG. 1). Apparatus 1600 is operable to carry outthe example methods described with reference to FIGS. 3 and 4, andpossibly any other processes or methods disclosed herein. It is also tobe understood that the methods of FIGS. 3 and 4 are not necessarilycarried out solely by apparatus 1600. At least some operations of themethod can be performed by one or more other entities.

Virtual apparatus 1600 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments.

In some implementations, the processing circuitry may be used to causereceiving unit 1602, determining unit 1604, removing unit 1606, and anyother suitable units of apparatus 1600 to perform correspondingfunctions according one or more embodiments of the present disclosure.

As illustrated in FIG. 5, apparatus 1600 includes receiving unit 1602configured to receive measurement configuration from a network node.Apparatus 1600 also includes determining unit 1604 configured todetermine a measurement object includes a reconfigured CQD parameterthat changes the way the wireless device determines the quality of acell; determine a measurement object includes a reconfigured CQDparameter that changes the way the wireless device performs beammeasurements or selects beam measurements for reporting; and/ordetermine a portion of the previously stored measurement results werecomputed based on the reconfigured CQD parameter. Apparatus 1600 alsoincludes removing unit 1606 configured to remove the portion of thepreviously stored measurement results and any associated timers or otherinformation.

FIG. 6 is a schematic block diagram illustrating a virtualizationenvironment 300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 300 hosted byone or more of hardware nodes 330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 320 are run invirtualization environment 300 which provides hardware 330 comprisingprocessing circuitry 360 and memory 390. Memory 390 containsinstructions 395 executable by processing circuitry 360 wherebyapplication 320 is operative to provide one or more of the features,benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose orspecial-purpose network hardware devices 330 comprising a set of one ormore processors or processing circuitry 360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 390-1 which may benon-persistent memory for temporarily storing instructions 395 orsoftware executed by processing circuitry 360. Each hardware device maycomprise one or more network interface controllers (NICs) 370, alsoknown as network interface cards, which include physical networkinterface 380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 390-2 having stored thereinsoftware 395 and/or instructions executable by processing circuitry 360.Software 395 may include any type of software including software forinstantiating one or more virtualization layers 350 (also referred to ashypervisors), software to execute virtual machines 340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 350 or hypervisor. Differentembodiments of the instance of virtual appliance 320 may be implementedon one or more of virtual machines 340, and the implementations may bemade in different ways.

During operation, processing circuitry 360 executes software 395 toinstantiate the hypervisor or virtualization layer 350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 350 may present a virtual operating platform thatappears like networking hardware to virtual machine 340.

As shown in FIG. 6, hardware 330 may be a standalone network node withgeneric or specific components. Hardware 330 may comprise antenna 3225and may implement some functions via virtualization. Alternatively,hardware 330 may be part of a larger cluster of hardware (e.g. such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 3100, which, among others, oversees lifecyclemanagement of applications 320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high-volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 340, and that part of hardware 330 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 340 on top of hardware networking infrastructure330 and corresponds to application 320 in FIG. 18.

In some embodiments, one or more radio units 3200 that each include oneor more transmitters 3220 and one or more receivers 3210 may be coupledto one or more antennas 3225. Radio units 3200 may communicate directlywith hardware nodes 330 via one or more appropriate network interfacesand may be used in combination with the virtual components to provide avirtual node with radio capabilities, such as a radio access node or abase station.

In some embodiments, some signaling can be effected with the use ofcontrol system 3230 which may alternatively be used for communicationbetween the hardware nodes 330 and radio units 3200.

With reference to FIG. 7, in accordance with an embodiment, acommunication system includes telecommunication network 410, such as a3GPP-type cellular network, which comprises access network 411, such asa radio access network, and core network 414. Access network 411comprises a plurality of base stations 412 a, 412 b, 412 c, such as NBs,eNBs, gNBs or other types of wireless access points, each defining acorresponding coverage area 413 a, 413 b, 413 c. Each base station 412a, 412 b, 412 c is connectable to core network 414 over a wired orwireless connection 415. A first UE 491 located in coverage area 413 cis configured to wirelessly connect to, or be paged by, thecorresponding base station 412 c. A second UE 492 in coverage area 413 ais wirelessly connectable to the corresponding base station 412 a. Whilea plurality of UEs 491, 492 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430,which may be embodied in the hardware and/or software of a standaloneserver, a cloud-implemented server, a distributed server or asprocessing resources in a server farm. Host computer 430 may be underthe ownership or control of a service provider or may be operated by theservice provider or on behalf of the service provider. Connections 421and 422 between telecommunication network 410 and host computer 430 mayextend directly from core network 414 to host computer 430 or may go viaan optional intermediate network 420. Intermediate network 420 may beone of, or a combination of more than one of, a public, private orhosted network; intermediate network 420, if any, may be a backbonenetwork or the Internet; in particular, intermediate network 420 maycomprise two or more sub-networks (not shown).

The communication system of FIG. 7 as a whole enables connectivitybetween the connected UEs 491, 492 and host computer 430. Theconnectivity may be described as an over-the-top (OTT) connection 450.Host computer 430 and the connected UEs 491, 492 are configured tocommunicate data and/or signaling via OTT connection 450, using accessnetwork 411, core network 414, any intermediate network 420 and possiblefurther infrastructure (not shown) as intermediaries. OTT connection 450may be transparent in the sense that the participating communicationdevices through which OTT connection 450 passes are unaware of routingof uplink and downlink communications. For example, base station 412 maynot or need not be informed about the past routing of an incomingdownlink communication with data originating from host computer 430 tobe forwarded (e.g., handed over) to a connected UE 491. Similarly, basestation 412 need not be aware of the future routing of an outgoinguplink communication originating from the UE 491 towards the hostcomputer 430.

FIG. 8 illustrates an example host computer communicating via a basestation with a user equipment over a partially wireless connection,according to certain embodiments. Example implementations, in accordancewith an embodiment of the UE, base station and host computer discussedin the preceding paragraphs will now be described with reference to FIG.8. In communication system 500, host computer 510 comprises hardware 515including communication interface 516 configured to set up and maintaina wired or wireless connection with an interface of a differentcommunication device of communication system 500. Host computer 510further comprises processing circuitry 518, which may have storageand/or processing capabilities. In particular, processing circuitry 518may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 510further comprises software 511, which is stored in or accessible by hostcomputer 510 and executable by processing circuitry 518. Software 511includes host application 512. Host application 512 may be operable toprovide a service to a remote user, such as UE 530 connecting via OTTconnection 550 terminating at UE 530 and host computer 510. In providingthe service to the remote user, host application 512 may provide userdata which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in atelecommunication system and comprising hardware 525 enabling it tocommunicate with host computer 510 and with UE 530. Hardware 525 mayinclude communication interface 526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 500, as well as radiointerface 527 for setting up and maintaining at least wirelessconnection 570 with UE 530 located in a coverage area (not shown in FIG.8) served by base station 520. Communication interface 526 may beconfigured to facilitate connection 560 to host computer 510. Connection560 may be direct, or it may pass through a core network (not shown inFIG. 8) of the telecommunication system and/or through one or moreintermediate networks outside the telecommunication system. In theembodiment shown, hardware 525 of base station 520 further includesprocessing circuitry 528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 520 further has software 521 storedinternally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to.Its hardware 535 may include radio interface 537 configured to set upand maintain wireless connection 570 with a base station serving acoverage area in which UE 530 is currently located. Hardware 535 of UE530 further includes processing circuitry 538, which may comprise one ormore programmable processors, application-specific integrated circuits,field programmable gate arrays or combinations of these (not shown)adapted to execute instructions. UE 530 further comprises software 531,which is stored in or accessible by UE 530 and executable by processingcircuitry 538. Software 531 includes client application 532. Clientapplication 532 may be operable to provide a service to a human ornon-human user via UE 530, with the support of host computer 510. Inhost computer 510, an executing host application 512 may communicatewith the executing client application 532 via OTT connection 550terminating at UE 530 and host computer 510. In providing the service tothe user, client application 532 may receive request data from hostapplication 512 and provide user data in response to the request data.OTT connection 550 may transfer both the request data and the user data.Client application 532 may interact with the user to generate the userdata that it provides.

It is noted that host computer 510, base station 520 and UE 530illustrated in FIG. 8 may be similar or identical to host computer 430,one of base stations 412 a, 412 b, 412 c and one of UEs 491, 492 of FIG.7, respectively. This is to say, the inner workings of these entitiesmay be as shown in FIG. 5 and independently, the surrounding networktopology may be that of FIG. 7.

In FIG. 8, OTT connection 550 has been drawn abstractly to illustratethe communication between host computer 510 and UE 530 via base station520, without explicit reference to any intermediary devices and theprecise routing of messages via these devices. Network infrastructuremay determine the routing, which it may be configured to hide from UE530 or from the service provider operating host computer 510, or both.While OTT connection 550 is active, the network infrastructure mayfurther take decisions by which it dynamically changes the routing(e.g., based on load balancing consideration or reconfiguration of thenetwork).

Wireless connection 570 between UE 530 and base station 520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 530 using OTT connection 550,in which wireless connection 570 forms the last segment. More precisely,the teachings of these embodiments may improve the signaling overheadand reduce latency, which may provide faster internet access for users.

A measurement procedure may be provided for monitoring data rate,latency and other factors on which the one or more embodiments improve.There may further be an optional network functionality for reconfiguringOTT connection 550 between host computer 510 and UE 530, in response tovariations in the measurement results. The measurement procedure and/orthe network functionality for reconfiguring OTT connection 550 may beimplemented in software 511 and hardware 515 of host computer 510 or insoftware 531 and hardware 535 of UE 530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection 550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above or supplying values ofother physical quantities from which software 511, 531 may compute orestimate the monitored quantities. The reconfiguring of OTT connection550 may include message format, retransmission settings, preferredrouting etc.; the reconfiguring need not affect base station 520, and itmay be unknown or imperceptible to base station 520. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 510's measurements of throughput, propagationtimes, latency and the like. The measurements may be implemented in thatsoftware 511 and 531 causes messages to be transmitted, in particularempty or ‘dummy’ messages, using OTT connection 550 while it monitorspropagation times, errors etc.

FIG. 9 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 9will be included in this section.

In step 610, the host computer provides user data. In substep 611 (whichmay be optional) of step 610, the host computer provides the user databy executing a host application. In step 620, the host computerinitiates a transmission carrying the user data to the UE. In step 630(which may be optional), the base station transmits to the UE the userdata which was carried in the transmission that the host computerinitiated, in accordance with the teachings of the embodiments describedthroughout this disclosure. In step 640 (which may also be optional),the UE executes a client application associated with the hostapplication executed by the host computer.

FIG. 10 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 10will be included in this section.

In step 710 of the method, the host computer provides user data. In anoptional substep (not shown) the host computer provides the user data byexecuting a host application. In step 720, the host computer initiates atransmission carrying the user data to the UE. The transmission may passvia the base station, in accordance with the teachings of theembodiments described throughout this disclosure. In step 730 (which maybe optional), the UE receives the user data carried in the transmission.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section.

In step 810 (which may be optional), the UE receives input data providedby the host computer. Additionally, or alternatively, in step 820, theUE provides user data. In substep 821 (which may be optional) of step820, the UE provides the user data by executing a client application. Insubstep 811 (which may be optional) of step 810, the UE executes aclient application which provides the user data in reaction to thereceived input data provided by the host computer. In providing the userdata, the executed client application may further consider user inputreceived from the user. Regardless of the specific manner in which theuser data was provided, the UE initiates, in substep 830 (which may beoptional), transmission of the user data to the host computer. In step840 of the method, the host computer receives the user data transmittedfrom the UE, in accordance with the teachings of the embodimentsdescribed throughout this disclosure.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 7 and 8. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section.

In step 910 (which may be optional), in accordance with the teachings ofthe embodiments described throughout this disclosure, the base stationreceives user data from the UE. In step 920 (which may be optional), thebase station initiates transmission of the received user data to thehost computer. In step 930 (which may be optional), the host computerreceives the user data carried in the transmission initiated by the basestation.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Modifications, additions, or omissions may be made to the systems andapparatuses disclosed herein without departing from the scope of theinvention. The components of the systems and apparatuses may beintegrated or separated. Moreover, the operations of the systems andapparatuses may be performed by more, fewer, or other components.Additionally, operations of the systems and apparatuses may be performedusing any suitable logic comprising software, hardware, and/or otherlogic. As used in this document, “each” refers to each member of a setor each member of a subset of a set.

Modifications, additions, or omissions may be made to the methodsdisclosed herein without departing from the scope of the invention. Themethods may include more, fewer, or other steps. Additionally, steps maybe performed in any suitable order.

The foregoing description sets forth numerous specific details. It isunderstood, however, that embodiments may be practiced without thesespecific details. In other instances, well-known circuits, structuresand techniques have not been shown in detail in order not to obscure theunderstanding of this description. Those of ordinary skill in the art,with the included descriptions, will be able to implement appropriatefunctionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to implement such feature, structure, orcharacteristic in connection with other embodiments, whether or notexplicitly described.

Although this disclosure has been described in terms of certainembodiments, alterations and permutations of the embodiments will beapparent to those skilled in the art. Accordingly, the above descriptionof the embodiments does not constrain this disclosure. Other changes,substitutions, and alterations are possible without departing from thespirit and scope of this disclosure, as defined by the claims below.

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   1×RTT CDMA2000 1×Radio Transmission Technology    -   3GPP 3rd Generation Partnership Project    -   5G 5th Generation    -   ABS Almost Blank Subframe    -   ARQ Automatic Repeat Request    -   AWGN Additive White Gaussian Noise    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   CA Carrier Aggregation    -   CC Carrier Component    -   CCCH SDU Common Control Channel SDU    -   CDMA Code Division Multiplexing Access    -   CGI Cell Global Identifier    -   CIR Channel Impulse Response    -   CN Core Network    -   CP Cyclic Prefix    -   CPICH Common Pilot Channel    -   CPICH Ec/No CPICH Received energy per chip divided by the power        density in the band    -   CQI Channel Quality information    -   CRC Cyclic Redundancy Check    -   C-RNTI Cell RNTI    -   CSI Channel State Information    -   CSI-RS CSI Reference Signal    -   DCCH Dedicated Control Channel    -   DCI Downlink Control Information    -   DL Downlink    -   DM Demodulation    -   DMRS Demodulation Reference Signal    -   DRX Discontinuous Reception    -   DTX Discontinuous Transmission    -   DTCH Dedicated Traffic Channel    -   DUT Device Under Test    -   E-CID Enhanced Cell-ID (positioning method)    -   E-SMLC Evolved-Serving Mobile Location Centre    -   ECGI Evolved CGI    -   eNB E-UTRAN NodeB    -   ePDCCH enhanced Physical Downlink Control Channel    -   E-SMLC evolved Serving Mobile Location Center    -   ETWS Earthquake and Tsunami Warning System    -   E-UTRA Evolved UTRA    -   E-UTRAN Evolved UTRAN    -   FDD Frequency Division Duplex    -   GERAN GSM EDGE Radio Access Network    -   gNB Base station in NR    -   GNSS Global Navigation Satellite System    -   GSM Global System for Mobile communication    -   HARQ Hybrid Automatic Repeat Request    -   HF High Frequency/High Frequencies    -   HO Handover    -   HSPA High Speed Packet Access    -   HRPD High Rate Packet Data    -   IMSI International Mobile Subscriber Identity    -   LOS Line of Sight    -   LPP LTE Positioning Protocol    -   LTE Long-Term Evolution    -   MAC Medium Access Control    -   MBMS Multimedia Broadcast Multicast Services    -   MBSFN Multimedia Broadcast multicast service Single Frequency        Network    -   MBSFN ABS MBSFN Almost Blank Subframe    -   MDT Minimization of Drive Tests    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   NPDCCH Narrowband Physical Downlink Control Channel    -   NR New Radio    -   OCNG OFDMA Channel Noise Generator    -   OFDM Orthogonal Frequency Division Multiplexing    -   OFDMA Orthogonal Frequency Division Multiple Access    -   OSS Operations Support System    -   OTDOA Observed Time Difference of Arrival    -   O&M Operation and Maintenance    -   PBCH Physical Broadcast Channel    -   P-CCPCH Primary Common Control Physical Channel    -   PCell Primary Cell    -   PCFICH Physical Control Format Indicator Channel    -   PDCCH Physical Downlink Control Channel    -   PDP Profile Delay Profile    -   PDSCH Physical Downlink Shared Channel    -   PGW Packet Gateway    -   PHICH Physical Hybrid-ARQ Indicator Channel    -   PLMN Public Land Mobile Network    -   PMI Precoder Matrix Indicator    -   PI Paging Indicator    -   PO Paging Occasion    -   PRACH Physical Random Access Channel    -   P-RNTI Paging RNTI    -   PRS Positioning Reference Signal    -   PSS Primary Synchronization Signal    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   RACH Random Access Channel    -   QAM Quadrature Amplitude Modulation    -   RAN Radio Access Network    -   RAR Random Access Response    -   RA-RNTI Random Access RNTI    -   RNA RAN Notification Area    -   RNTI Radio Network Temporary Identifier    -   RAT Radio Access Technology    -   RLM Radio Link Management    -   RNC Radio Network Controller    -   RNTI Radio Network Temporary Identifier    -   RRC Radio Resource Control    -   RRM Radio Resource Management    -   RS Reference Signal    -   RSCP Received Signal Code Power    -   RSRP Reference Symbol Received Power OR Reference Signal        Received Power    -   RSRQ Reference Signal Received Quality OR Reference Symbol        Received Quality    -   RSSI Received Signal Strength Indicator    -   RSTD Reference Signal Time Difference    -   SAE System Architecture Evolution    -   SCH Synchronization Channel    -   SCell Secondary Cell    -   SDU Service Data Unit    -   SFN System Frame Number or Single Frequency Network    -   SGW Serving Gateway    -   SI System Information    -   SIB System Information Block    -   SNR Signal to Noise Ratio    -   SON Self Optimized Network    -   SS Synchronization Symbol    -   SSS Secondary Synchronization Signal    -   S-TMSI SAE-TMSI    -   TDD Time Division Duplex    -   TDOA Time Difference of Arrival    -   TMSI Temporary Mobile Subscriber Identity    -   TRP Transmission/Reception Point    -   TOA Time of Arrival    -   TSS Tertiary Synchronization Signal    -   TTI Transmission Time Interval    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunication System    -   USIM Universal Subscriber Identity Module    -   UTDOA Uplink Time Difference of Arrival    -   UTRA Universal Terrestrial Radio Access    -   UTRAN Universal Terrestrial Radio Access Network    -   WCDMA Wide CDMA    -   WLAN Wide Local Area Network

1. A method performed by a wireless device for updating measurementconfiguration, the method comprising receiving a measurementconfiguration from a network node, the measurement configurationcomprising a measurement object that includes at least one cell qualityderivation parameter, wherein the wireless device has previously storedmeasurement results associated with the measurement object; determiningthe measurement object includes a reconfigured cell quality derivationparameter that changes the way the wireless device determines thequality of a cell; determining a portion of the previously storedmeasurement results were computed based on the reconfigured cell qualityderivation parameter; and removing the portion of the previously storedmeasurement results.
 2. The method of claim 1, wherein removing theportion of the previously stored measurement results further comprisesresetting timers and removing measurement information associated withthe removed measurement results.
 3. The method of claim 1, wherein themeasurement object includes a first cell quality derivation parameterindicating a maximum number of beams to average for cell measurementresults and a second cell quality derivation parameter indicating asignal quality threshold for selecting additional beams to average forcell measurement results; and wherein determining the measurement objectincludes a reconfigured parameter that changes the way the wirelessdevice determines the quality of a cell comprises determining themeasurement object includes at least one of the first cell qualityderivation parameter and the second cell quality derivation parameter.4. The method of claim 3, wherein determining the measurement objectincludes a reconfigured parameter that changes the way the wirelessdevice determines the quality of a cell comprises determining at leastone of the first cell quality derivation parameter and the second cellquality derivation parameter is changed.
 5. The method of claim 3,wherein determining the measurement object includes a reconfiguredparameter that changes the way the wireless device determines thequality of a cell comprises determining: the first parameter is changed;or the second parameter is changed, and the first parameter is changedto a value greater than one or the first parameter was not changed butwas greater than one before receiving the measurement configuration. 6.The method of claim 3, wherein: the first cell quality derivationparameter comprises a maximum number of beams to average for cellmeasurements based on a channel state information reference signal(CSI-RS) and the second cell quality derivation parameter comprises asignal quality threshold for selecting additional beams to average basedon a CSI-RS; or the first cell quality derivation parameter comprises amaximum number of beams to average for cell measurements based on asynchronization symbol (SS) and the second cell quality derivationparameter comprises a signal quality threshold for selecting additionalbeams to average based on a SS.
 7. The method of claim 6, wherein: themeasurement configuration further comprises a report configurationassociated with the measurement object, the report configurationcomprising an indication of a reference signal type, wherein thereference signal type is one of CSI-RS or SS; and determining themeasurement object includes a reconfigured parameter that changes theway the wireless device determines the quality of a cell furthercomprises determining that the first cell quality derivation parameterand the second cell quality derivation parameter are based on CSI-RS andthe reference signal type is CSI-RS, or determining that the first cellquality derivation parameter and the second cell quality derivationparameter are based on SS and the reference signal type is SS.
 8. Awireless device operable to update a measurement configuration, thewireless device comprising processing circuitry operable to: receive ameasurement configuration from a network node, the measurementconfiguration comprising a measurement object that includes at least onecell quality derivation parameter, wherein the wireless device haspreviously stored measurement results associated with the measurementobject; determine the measurement object includes a reconfigured cellquality derivation parameter that changes the way the wireless devicedetermines the quality of a cell; determine a portion of the previouslystored measurement results were computed based on the reconfigured cellquality derivation parameter; and remove the portion of the previouslystored measurement results.
 9. The wireless device of claim 8, whereinthe processing circuitry is further operable to reset timers and removemeasurement information associated with the removed measurement results.10. The wireless device of claim 8, wherein the measurement objectincludes a first cell quality derivation parameter indicating a maximumnumber of beams to average for cell measurement results and a secondcell quality derivation parameter indicating a signal quality thresholdfor selecting additional beams to average for cell measurement results;and wherein the processing circuitry is operable to determine themeasurement object includes a reconfigured parameter that changes theway the wireless device determines the quality of a cell by determiningthe measurement object includes at least one of the first cell qualityderivation parameter and the second cell quality derivation parameter.11. The wireless device of claim 10, wherein the processing circuitry isoperable to determine the measurement object includes a reconfiguredparameter that changes the way the wireless device determines thequality of a cell by determining at least one of the first cell qualityderivation parameter and the second cell quality derivation parameter ischanged.
 12. The wireless device of claim 10, wherein the processingcircuitry is operable to determine the measurement object includes areconfigured parameter that changes the way the wireless devicedetermines the quality of a cell by determining: the first parameter ischanged; or the second parameter is changed, and the first parameter ischanged to a value greater than one or the first parameter was notchanged but was greater than one before receiving the measurementconfiguration.
 13. The wireless device of claim 10, wherein: the firstcell quality derivation parameter comprises a maximum number of beams toaverage for cell measurements based on a channel state informationreference signal (CSI-RS) and the second cell quality derivationparameter comprises a signal quality threshold for selecting additionalbeams to average based on a CSI-RS; or the first cell quality derivationparameter comprises a maximum number of beams to average for cellmeasurements based on a synchronization symbol (SS) and the second cellquality derivation parameter comprises a signal quality threshold forselecting additional beams to average based on a SS.
 14. The wirelessdevice of claim 13, wherein: the measurement configuration furthercomprises a report configuration associated with the measurement object,the report configuration comprising an indication of a reference signaltype, wherein the reference signal type is one of CSI-RS or SS; andwherein the processing circuitry is operable to determine themeasurement object includes a reconfigured parameter that changes theway the wireless device determines the quality of a cell by determiningthat the first cell quality derivation parameter and the second cellquality derivation parameter are based on CSI-RS and the referencesignal type is CSI-RS, or determining that the first cell qualityderivation parameter and the second cell quality derivation parameterare based on SS and the reference signal type is SS.
 15. A methodperformed by a wireless device for updating measurement configuration,the method comprising receiving a measurement configuration from anetwork node, the measurement configuration comprising a measurementobject that includes at least one cell quality derivation parameter,wherein the wireless device has previously stored measurement resultsassociated with the measurement object; determining the measurementobject includes a reconfigured cell quality derivation parameter thatchanges the way the wireless device performs beam measurements orselects beam measurements for reporting; determining a portion of thepreviously stored measurement results were computed based on thereconfigured cell quality derivation parameter; and removing the portionof the previously stored measurement results.
 16. The method of claim15, wherein removing the portion of the previously stored measurementresults further comprises resetting timers and removing measurementinformation associated with the removed measurement results.
 17. Themethod of claim 15, wherein the cell quality derivation parametercomprises a signal quality threshold for selecting additional beams toaverage for cell measurement results; and wherein determining themeasurement object includes a reconfigured parameter that changes theway the wireless device performs beam measurements or selects beammeasurements for reporting comprises determining the measurement objectincludes the cell quality derivation parameter.
 18. The method of claim17, wherein determining the measurement object includes a reconfiguredparameter that changes the way the wireless device performs beammeasurements or selects beam measurements for reporting comprisesdetermining the cell quality derivation parameter is changed.
 19. Themethod of claim 17, wherein the cell quality derivation parametercomprises a signal quality threshold for selecting additional beams toaverage based on a CSI-RS or a signal quality threshold for selectingadditional beams to average based on a SS.
 20. The method of claim 19,wherein: the measurement configuration further comprises a reportconfiguration associated with the measurement object, the reportconfiguration comprising an indication of a reference signal type,wherein the reference signal type is one of CSI-RS or SS; anddetermining the measurement object includes a reconfigured parameterthat changes the way the wireless device performs beam measurements orselects beam measurements for reporting further comprises determiningthat the cell quality derivation parameter is based on CSI-RS and thereference signal type is CSI-RS, or determining that the cell qualityderivation parameter is based on SS and the reference signal type is SS.21.-28. (canceled)